21 APR 2011 by ideonexus

 Peter Norvig: How Well Does the Program Run When it Isn't...

And think about failure modes—I remember one of the great lessons I got about programming was when I showed up at the airport at Heathrow, and there was a power failure and none of the computers were working. But my plane was on time. Somehow they had gotten print-outs of all the flights. 1 don't know where—there must have been some computer off-site, i don't know whether they printed them that morning or if they had a procedure of always printing them the night before and sending them ...
  1  notes

An important use-case for any software, what's the work-around for when the program isn't running?

03 JAN 2011 by ideonexus

 ReFactoring: Kill Your Darlings

In software design, when you find yourself feeling particularly proud of a neat little bit of design or code, stop and ask yourself how someone who didn't give birth to it will regard it. If it turns out to be overwrought or too slick for the need, you should probably kill your darling and replace it with an ordinary solution that others can actually use, and not just marvel at. Darlings are sometimes characterized as being "ever so clever." For an example, the phrase "ever so clever" is ever...
Folksonomies: programming refactoring
Folksonomies: programming refactoring
 2  2  notes

A good principle in software design, related to egoless programming, where developers don't get personally attached to their code, making it easier to cut for more elegant solutions